Network-initiated data transfer in a mobile network

ABSTRACT

A method for IP[=Internet Protocol] communication to/from a mobile terminal via a network element in a mobile network. The mobile terminal uses an in-band trigger for establishing an IP connection. The network element uses an out-band trigger ( 3 - 8 ) for initiating IP connection establishment. The mobile terminal responding to the out-band trigger by using an in-band trigger for establishing the IP connection ( 3 - 10 ). Afte the data transfer ( 3 - 12 ), the mobile terminal and the network element maintain the IP connection for a predetermined time after the latest transaction ( 3 - 14 ).

A. BACKGROUND OF THE INVENTION

The invention relates to techniques which are colloquially referred to as pushing data. Expressed more formally, the invention relates to methods, equipment and program products for network-initiated data transfer in a packet-switched mobile network.

In a packet-switched mobile network, a mobile terminal does is not normally assigned a dedicated circuit-switched connection. Instead, the network establishes and maintains a session for the terminal, and data packets are sent when necessary. In order to integrate mobile terminals with office applications, it is becoming increasingly popular to maintain Internet Protocol (IP) connections over packet data channels in packet-switched mobile networks. Maintaining an IP connection to/from a mobile terminal is desirable in order to keep data banks synchronized between the mobile terminal and an office computer, for example.

Maintaining an IP connection in packet-switched mobile networks involves certain problems, however. For example, it consumes the mobile terminal's battery. Further, many networks apply operator-defined policies to break connections after a certain period of inactivity. When the IP connection to/from the mobile terminal is disconnected, database synchronization is impossible before connection re-establishment. Connection re-establishment must be initiated from the mobile terminal's side, the network cannot initiate connection re-establishment.

But connection re-establishment involves further expenses in tariff and/or battery consumption. Yet further, since the network cannot initiate re-establishment of the IP connection, network-initiated data synchronization must be initiated by means of an out-band trigger, i.e., signalling independent from the Internet Protocol. A short message service (SMS) and its derivatives are examples of theoretically suitable out-band triggering mechanisms. But a single GSM-compliant short message can only transfer approximately 160 characters, which means that it is impracticable to transfer actual data in the trigger message. This has the consequence that the subscriber must bear the expenses and delays in re-establishing the IP connection.

B. BRIEF DESCRIPTION OF THE INVENTION

An object of the present invention is to provide a method and an apparatus for implementing the method so as to alleviate the above disadvantages. The object of the invention is achieved by the methods and equipment which are characterized by what is stated in the independent claims. The dependent claims relate to specific embodiments of the invention.

The invention is based on the idea that a mobile terminal uses an in-band trigger for establishing an IP connection. The network element, when it needs to communicate with the mobile terminal, uses an existing IP connection if one is available; and if not, uses an out-band trigger for initiating the IP connection establishment. The mobile terminal responds to the out-band trigger by using an in-band trigger for establishing the IP connection. The IP connection is maintained for a predetermined time after the latest transaction (in either direction).

If no out-band trigger for initiating IP connection establishment is available, the mobile terminal enters a periodic polling mode, wherein it periodically sends inquires to or via the network element for data items to be synchronized.

An aspect of the invention is a method according to claim 1. Another aspect of the invention is a method according to claim 2. Other aspects of the invention relate to computer systems or program products for implementing the above methods.

C. BRIEF DESCRIPTION OF THE DRAWINGS

In the following the invention will be described in greater detail by means of specific embodiments with reference to the attached drawings, in which:

FIG. 1 shows an exemplary network arrangement in which the invention can be used;

FIG. 2 shows a flowchart illustrating the principle of the invention as seen from the point of view of the network element; and

FIG. 3 shows a flowchart illustrating the principle of the invention as seen from the point of view of the mobile terminal.

D. DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

The invention is applicable to virtually any mobile network architecture. The mobile network may be based on GPRS, 1xRTT or EVDO technologies, for example. The invention can also be implemented as part of a push-type mobile e-mail system, particularly in a consumer e-mail system, in which optimization of network resources is important because of the large number of users.

FIG. 1 shows an exemplary system architecture which is supported by the owner of the present application. This system supports synchronization of e-mail messages and/or calendar items and/or other information between a host system and a mobile terminal.

Reference numeral 100 denotes a host system that is able to send an receive e-mail messages. Reference numeral 102 denotes a mobile terminal, also able to send an receive e-mail messages. The e-mail messages may originate or terminate at external e-mail terminals, one of which is denoted by reference numeral 104.The invention aims at improving cooperation between the host system 100 and mobile terminal 102 such that they can use a single e-mail account as transparently as possible. This means, for example, that the users of the external e-mail terminals 104, when sending or receiving e-mail, do not need to know if the user of the host system 100 actually uses the host system 100 or the mobile terminal 102 to communicate via e-mail. The transparency also means that e-mail manipulation at the mobile terminal 102 has, as far as possible, the same effect as the corresponding e-mail manipulation at the host system 100. For example, e-mail messages read at the mobile terminal 102 should preferably be marked as read at the host system.

Reference numeral 106 denotes a data network, such as an IP (Internet Protocol) network, which may be the common Internet or its closed subnetworks, commonly called intranets or extranets. Reference numeral 108 denotes an e-mail server and its associated database. There may be separate e-mail servers and/or server addresses for incoming and outgoing e-mail. The database stores an e-mail account, addressable by means of an e-mail address, that appears as a mailbox to the owner of the e-mail account. In order to communicate with mobile terminals 102, the data network 106 is connected, via a gateway 112 to an access network 114. The access network comprises a set of base stations 116 to provide wireless coverage over a wireless interface 118 to the mobile terminals 102.

Reference numeral 110 denotes a messaging centre that is largely responsible for providing the above-mentioned transparency between the host system 100 and the mobile terminal 102. The system architecture also comprises a connectivity function 120, whose task is to push e-mail messages to the mobile terminal. In the embodiment shown in FIG. 1, the connectivity function 120 is considered a physically integral but logically distinct element of the messaging centre 110.

The mobile terminal 102 may be a pocket or laptop computer with a radio interface, a smart cellular telephone, or the like. Depending on implementation, the host system 100, if present, may have different roles. In some implementations the host system 100 is optional and may be a conventional office computer that merely acts as the mobile terminal user's principal computer and e-mail terminal. In other implementations the host system may act as a platform for a single user's connectivity function, in addition to being an office computer. In yet other implementations the host system 100 may comprise the connectivity function for several users. Thus it is a server instead of a normal office computer.

We assume here that the access network 114 is able to establish and maintain a IP connection 122 between the messaging centre 110 and the mobile terminal 102.

FIG. 1 shows an embodiment in which the messaging centre 110 is largely responsible for e-mail transport to/from the mobile terminal 102 via the access network 114, while a separate connectivity function 120 is responsible for data security issues. The connectivity function 120 may be physically attached to or co-located with the messaging centre 110, but they are logically separate elements. Indeed, a definite advantage of the separate connectivity function 120 is that it can be detached from the messaging centre, for instance, within the company that owns the host system 100 or the e-mail server 108. For a small number of users, the connectivity function 120 can be installed in each host system 100, or the host system 100 can be interpreted as a separate server configured to support multiple users. It is even possible to implement some or all the above-mentioned options. This means, for example, that there is one or more messaging centres 110 that offer services to several network operators, or they may be a dedicated messaging centre for each network operator (somewhat analogous to short messaging centres). Each messaging centre 110 may have an integral connectivity function 120 to support users who don't wish to install a separate connectivity function in a host system 100. For users who do install a separate connectivity function 120 in their host systems 100, such connectivity functions bypass the connectivity function in the messaging centre 110 and address the messaging centre 110 directly.

A real e-mail system supports a large number of mobile terminals 102 and IP connections 122. In order to keep track of which e-mail account and which IP connection belongs to which mobile terminal, the messaging centre 110 and the connectivity function collectively maintain an association 124, 124′ for each supported mobile terminal. Basically, each association 124,124′ joins three fields, namely an e-mail address 124A assigned to the mobile terminal or its user, encryption information 124C and a temporary wireless identity 124D of the mobile terminal in the access network. The embodiment shown in FIG. 1 also employs a terminal identifier 124B which may be the same as the e-mail address 124A of the mobile terminal 102, in which case the association 124 actually associates three information items. Alternatively, the terminal identifier 124B may be an identifier arbitrarily assigned to the mobile terminal. In a preferred implementation the terminal identifier 124B is the mobile terminal's equipment identifier or its derivative. The encryption information 124C is preferably related to the mobile terminal's equipment identity and is preferably generated by the mobile terminal itself, so as to ensure that no other terminal besides the one used for creating the encryption information 124C will be able to decrypt incoming encrypted e-mail messages. The temporary wireless identity 124D may be the identifier of the IP connection 122 to the mobile station.

In the above-described system, the messaging centre 110 and connectivity function 120 were arranged to support a fairly large number of users of e-mail and/or calendar data. In order to satisfy the needs of the present invention, virtually any communication server able to maintain an IP connection to the mobile terminal can be used.

In order to provide out-band triggers, the network arrangement is operationally coupled to a network element able to communicate to the mobile terminal even in the absence of an IP connection. In the network arrangement shown in Figure, such a network element is embodied as a short message service centre (SMSC) 126. Because the IP connection cannot be initiated from the network side, the messaging centre 110 (or any other communication server) must request the mobile terminal 102 to establish the IP connection, for example when data needs to be synchronized between the mobile terminal and some other node, such as the host system 100. Such a request to establish the IP connection can be sent in the form of a connectionless message, such as a short message or one of its derivatives, for example, a multimedia message.

FIG. 2 shows a flowchart illustrating the principle of the invention as seen from the point of view of a network element, such as the messaging centre 110 shown in FIG. 1, or some other element or server communicating with the mobile terminal. Step 2-2 is a loop in which the network element waits for a need to transfer data to the mobile terminal. In step 2-4 the network element determines if an IP connection to the mobile terminal is available. If yes, the IP connection will be used in step 2-6. After step 2-6 the process continues to step 2-16 in which the IP connection will be kept active for a predetermined time after, in order to avoid the expenses incurred in re-establishing a discontinued IP connection.

If no IP connection to the mobile terminal was not available in step 2-4, the process continues to step 2-8, in which the network element determines if an out-band triggering means, such as a short message service, is available. If not, the process continues to step 2-10, in which the network element resorts to mobile-initiated polling. In other words, the network element has no means to initiate IP connection establishment to the mobile terminal and must wait for inquiries from the mobile terminal. On the other hand, if an out-band triggering means, such as a short message service, is available, it will be used in step 2-12. In response to the trigger, the mobile terminal establishes an IP connection which the network element will use in 2-14, after which the process continues to step 2-16.

FIG. 3 shows a flowchart illustrating the principle of the invention as seen from the point of view of the mobile terminal. In step 3-2 the mobile terminal determines if an out-band triggering means is available. If not, the mobile terminal knows that the network element cannot request IP connection establishment, and in step 3-4 the mobile terminal enters a periodic polling mode, in which it periodically polls the network element for new information.

The mobile terminal makes the test in step 3-2 not for its own benefit but for the network element's, because the mobile terminal can always initiate IP connection establishment. But if no out-band triggering means is available, the mobile terminal knows that it cannot expect a request from the network element to establish an IP connection, which is why it should periodically poll the network element for new data.

When the system is in the periodic polling mode, at certain periodic intervals, the mobile terminal establishes an IP connection for inquiring the network element for new data, even if the mobile terminal itself has no data to send. If the network element has data to send, the IP connection is preferably kept active for a predetermined time after the latest data transfer. This procedure will be further described in connection with step 3-14.

In step 3-6, if the mobile terminal detects a need to transfer data, it proceeds to step 3-10 to establish an IP connection with the network element. Likewise, the IP connection establishment is initiated if in step 3-8 an out-band trigger is received from the network element. After the IP connection establishment in step 3-10, the mobile terminal transfers data in step 3-12, and in step 3-14 it keeps the IP connection active for a predetermined time after the latest transaction (in either direction).

In steps and 2-16 and 3-14, the IP connection is kept active for a predetermined time after the latest transaction (in either direction), in order to avoid the expenses in re-establishing a disconnected IP connection. This step can be implemented, for example, by means of two timers (physical or logical). Let us assume, for example, that the network disconnects IP connections after an inactivity period of 5 minutes. Let us further assume that, for the sake of economy and convenience, the IP connection will be maintained for 15 minutes after the latest transaction. After each transaction, both timers will be started. When the 5-minute timer expires, a keep-alive message is sent to the other party. A keep-alive message is a message sent for the purpose of preventing the network from disconnecting the IP connection. When the keep-alive message is sent, the 5-minute timer is again restarted, until the 15-minute timer expires, after which the keep-alive messages will no longer be sent.

It is readily apparent to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The invention and its embodiments are not limited to the examples described above but may vary within the scope of the claims. 

1. A method for IP [=Internet Protocol] communication to/from a mobile terminal via a network element in a mobile network, the method comprising: the mobile terminal using an in-band trigger for establishing an IP connection; the network element using an out-band trigger for initiating IP connection establishment; the mobile terminal responding to the out-band trigger by using an in-band trigger for establishing the IP connection; maintaining the IP connection for a predetermined time after the latest transaction in either direction.
 2. A method for IP communication to/from a mobile terminal in a mobile network, the method comprising: the mobile terminal using an in-band trigger for establishing an IP connection; in response to detecting that no out-band trigger for initiating IP connection establishment is available, the mobile terminal entering a periodic polling mode, wherein the mobile terminal periodically inquires via a network element for data items to be synchronized; in response to receiving one or more data items to be synchronized, the mobile terminal maintaining the IP connection for a predetermined time after receiving the one or more data items to be synchronized.
 3. A mobile terminal for a mobile network, the mobile terminal comprising: means for using an in-band trigger for establishing an IP connection; means for responding to an out-band trigger from a network element for initiating IP connection establishment; means for responding to the out-band trigger by using an in-band trigger for establishing the IP connection.
 4. A mobile terminal according to claim 3, further comprising means for maintaining the IP connection for a predetermined time after the latest transaction.
 5. A mobile terminal for a mobile network, the mobile terminal comprising: means for using an in-band trigger for establishing an IP connection; means for entering a periodic polling mode in response to detecting that no out-band trigger for initiating IP connection establishment is available, the periodic polling mode comprising periodical inquires from the mobile terminal via a network element for data items to be synchronized.
 6. A mobile terminal according to claim 5, further comprising means, responsive to receiving one or more data items to be synchronized, for maintaining the IP connection for a predetermined time after receiving the one or more data items to be synchronized.
 7. A network element, connectable to a mobile network, for IP communication with a mobile terminal, the network element comprising: means for determining if an out-band trigger is available for causing the mobile terminal to initiate IP connection establishment; means, responsive to a determination that an out-band trigger is available, for sending the out-band trigger to the mobile terminal when a need to transfer data to the mobile terminal exists.
 8. A network element according to claim 7, further comprising means for responding to polling by the mobile terminal.
 9. A computer program product for a mobile terminal, the computer program product comprising program code instructions for causing the mobile terminal to carry out the steps of claim 1 when said computer program product is executed in the mobile terminal.
 10. A computer program product for a mobile terminal, the computer program product comprising program code instructions for causing the mobile terminal to carry out the steps of claim 2 when said computer program product is executed in the mobile terminal. 